Node-RED block in Snap4City Microservice library node-red-contrib-snap4city-developer is "service-search-by-municipality">
    <p>It allows to retrieve the set of services that are in a specific municipality. The services can be filtered as belonging
        to specific categories (e.g. Accomodation, Hotel, Restaurant etc)
    </p>

    <h3>Inputs</h3>
    A JSON with these parameters:

    <dl class="message-properties">
        <dt>municipality
            <span class="property-type">string</span>
        </dt>
        <dd> name of the municipality like FIRENZE, EMPOLI, PISA</dd>
        <dt>categories
            <span class="property-type">string</span>
        </dt>
        <dd> the list of categories of the services to be retrieved separated with semicolon, if omitted all kinds of services
            are returned. It can contain macro categories or categories, if a macro category is specified all categories
            in the macro category are used. The complete list of categories and macro categories can be retrieved on servicemap.disit.org</dd>
        <dt>maxresults
            <span class="property-type">number</span>
        </dt>
        <dd> maximum number of results to be returned (if parameter is missing 100 is assumed), if it is 0 all results are returned</dd>
        <dt>lang
            <span class="property-type">string</span>
        </dt>
        <dd> ISO 2 chars language code (e.g. “it”, “en”, “fr”, “de”, “es”) to be used for returned descriptions if available in
            multiple languages. Currently for languages other than “it” and “en” it returns “en” descriptions. (if parameter
            is missing “en” is assumed)</dd>
        <dt>geometry
            <span class="property-type">boolean</span>
        </dt>
        <dd> true/false, if true it returns a “hasGeometry” property for each service stating if the service has a complex WKT
            geometries (linestring, polygon) associated with it (if parameter is missing “false” is assumed)</dd>
    </dl>

    <h3>Outputs</h3>
    <ol class="node-ports">
        <li>ServiceUri Array
            <dl class="message-properties">
                <dd> Returns an array containing the servicesUri of each service found</dd>
            </dl>
        </li>
        <li>GeoJSON Results
            <dl class="message-properties">
                <dd> It returns the services split in three sections (BusStops , SensorSites, Services). Each section is provided
                    as GeoJSON “FeatureCollection”, the results are sorted by distance, additionally in each section the
                    “fullCount” property reports the full number of results available matching the query</dd>
            </dl>
        </li>
        <li> All services together
            <dl class="message-properties">
                <dd> It returns the services merge in Results section</dd>
            </dl>
        </li>
    </ol>

    <h3>Details</h3>
    <p>The node can receive a JSON with the parameters described in the Inputs section and with them generate the output JSON.
        If the values are not present in the input JSON, these are read by those in the configuration. If they are not present
        in either part, an error is generated for the necessary parameters.</p>